This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?
Blog
Recent Entries
Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!
The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.
For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.
Maria Jose Herrera
Maria Jose Herrera
September
18,
2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork
Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.
Luis Majano
Luis Majano
September
15,
2026
TestBox 7.1 Released : 47 New Ways to Assert, 29 of Them BoxLang-Only
TestBox 7.1.0 is here, and it is the largest single expansion of our assertion and expectation library since TestBox was born.
Luis Majano
Luis Majano
September
11,
2026
Add Your Comment
(4)
Feb 23, 2007 03:50:04 UTC
by Sana
Hi Luis,
I think 30 minutes, as sessions default expiry is 30 minutes, so this cookie should be 30 minutes expiry time.
Feb 23, 2007 07:29:14 UTC
by Dan Wilson
Luis,
Perhaps it could be left up to the user to clear the cookie when they have finished the debugging?
A link or a special URL perhaps to clear the cookie?
Dan
Feb 23, 2007 10:00:43 UTC
by reuben
I agree with Sana that the time out for a cookie should be defaulted to the session timeout. If you are working constantly on the site, the debug will last beyond 30 minutes. The big issue is that if you stop work and come back to the site, you don't always want debug still enabled. I think having it auto expire is a good thing.
Feb 23, 2007 10:24:47 UTC
by Luis Majano
Dan,
You can clear the cookie by just setting debugmode=false once you are done. But we all know that sometimes we are lazy and basically forget, like 90 year old brians!!
So an automatic timeout, would allow security and also peace of mind.
I think 30 minutes is reasonable. Any more suggestions.